Summary

Adds code-interpreter-go/, a full Go port of the Python code-interpreter service, alongside the existing implementation (the Python service is untouched, so both can run side by side during migration).

Same API surface and payloads: GET /health, POST /v1/execute, POST /v1/execute/stream (SSE output/result/error events), /v1/files CRUD, /v1/sessions with TTL-enforced teardown + reaper, and POST /v1/sessions/{id}/bash. Same environment-based configuration.

Benchmarks (Python vs Go)

Measured with the committed harness (benchmarks/, methodology and reproduction steps in benchmarks/README.md) on a 24-CPU Linux host; two full runs, medians shown as ranges. Both services ran natively with identical config and load.

The Python service plateaus under concurrency (GIL: 16-worker download throughput barely exceeds 1-worker); matching Go's 16-worker throughput would take ~6–8 uvicorn workers (~300–400 MiB RSS) vs one 43 MiB Go process.

Image sizes (compressed): the published Python image is 194 MB (registry-measured; 104 MB of that is the docker-ce layer, 45 MB the python base, ~38 MB venv/uv). The Go -slim image derives to ~45 MB (30 MB debian base + 13 MB gzipped binary) and the Go default to ~150 MB. Application payload: one 46 MB static binary vs 84 MB CPython + 129 MB venv.

Caveat: end-to-end /v1/execute latency is not benchmarked (needs a Docker daemon; the bench host had no CAP_SYS_ADMIN). It is dominated by container create/start, which both implementations pay identically; they differ in orchestration overhead (Python spawns ~6 docker-CLI subprocesses per execution, Go makes Engine API calls on one socket).

Key design changes vs. the Python service

• Docker Engine API instead of the docker CLI (github.com/docker/docker/client): typed not-found/conflict errors replace stderr-string heuristics, exec-attach with demultiplexed streams feeds SSE, and image pull happens over the API. File staging and workspace snapshots still run tar inside the container over the exec API, because /workspace is a tmpfs mount the engine's copy API writes past invisibly.
• PYTHON_EXECUTOR_DOCKER_RUN_ARGS is now a documented subset (--label, --env, --add-host, --dns, --ulimit) and the service fails fast at startup on unsupported flags instead of silently passing them through. PYTHON_EXECUTOR_DOCKER_BIN is no longer read; the daemon connection uses standard DOCKER_HOST et al.
• entrypoint.sh is built into the binary (internal/bootstrap): mode detection (kubernetes / external DOCKER_HOST / mounted socket / DinD), cgroup v2 nesting, nested dockerd launch + supervision, and readiness via SDK ping instead of docker info. The image runs the binary directly — no shell needed at runtime.
• Hardened, slimmer images: bases default to Docker Hardened Images from dhi.io (override via BUILD_IMAGE/RUNTIME_IMAGE), the Docker daemon is installed only for DinD support, and curl/gnupg/supervisor/bash are gone. SKIP_NESTED_DOCKER=1 builds support Docker-out-of-Docker with zero docker packages (the Python image needed the CLI for DooD).
• Kubernetes backend on client-go with SPDY exec — binary-safe streams remove the tar | base64 round-trip.
• Bug fix: ephemeral container keepalive was timeout_ms * 1000 seconds (multi-day sleeps on a crashed API); now timeout_ms/1000 + 10 seconds.
• Validation error bodies are {"detail": "<message>"} strings (not Pydantic's array format); status codes unchanged. /docs//redoc//openapi.json are not served.

Packaging & CI

• Two image variants per release, defined in docker-bake.hcl: onyxdotapp/code-interpreter-go:<version> (default, includes the Docker daemon — works in every deployment mode) and :<version>-slim (zero docker packages, for DooD/Kubernetes). docker buildx bake local builds the host's native platform for development.
• Release workflow builds each platform on a native runner (ubuntu-latest / ubuntu-24.04-arm, no QEMU), pushes by digest, and merges the multi-arch manifests with imagetools create. The Go build stage cross-compiles from $BUILDPLATFORM.
• New golang-checks CI job: gofmt / build / vet / unit tests, plus the real-daemon Docker executor e2e test against the runner's daemon.

Testing

• go build ./..., go vet ./..., gofmt clean; go test ./... green across all packages.
• Unit tests: image ref normalization, path validation, tar round-trips, incremental UTF-8 stream decoding with output caps, run-args parsing, container specs, file storage, bootstrap mode decision.
• httptest-based API tests with a fake executor mirroring tests/integration_tests coverage (execute, streaming SSE, files upload/download/list/delete incl. 413, sessions, bash, health).
• The Docker executor e2e test runs in CI against a real daemon (golang-checks job).
• Not verified yet: the image builds against the dhi.io bases (validate the refs/auth with a workflow_dispatch dry run before the first release) and the privileged DinD bootstrap path, which needs a --privileged deployment to exercise.

🤖 Generated with Claude Code